Auto draw flow

ABSTRACT

A computing device can automatically generate a flow diagram showing statuses that objects in a system can possess, and the possible transitions between these statuses. Using snapshots of database data, the device can determine how the statuses of these objects have changed over time. The device can analyze the data to suggest which database fields likely represent object status. The device can render the flow diagram to illustrate system states at different selected times. Each rendered flow diagram can indicate, for the selected time point, the quantity of objects that possessed each status at that time, and, for a selected time interval, the quantity of objects that changed from each status to each other status during that time interval. The statuses can be represented in the flow diagram as status bubbles having sizes that are based on the quantities of objects have those bubble&#39;s statuses at the selected time point.

CLAIM OF PRIORITY

The present application claims priority under 35 U.S.C. §119(e) to thefollowing patent applications, the contents of each of which areincorporated by reference herein: Provisional U.S. Patent ApplicationSer. No. 61/872,479, filed Aug. 30, 2013, and titled “FLOW FIELDS”;Provisional U.S. Patent Application Ser. No. 61/872,485, filed Aug. 30,2013, and titled “FLOW STATE TOTALS AND AUTO FLOW WAREHOUSING”;Provisional U.S. Patent Application Ser. No. 61/872,490, filed Aug. 30,2013, and titled “FLOW PIPE TOTALS”; and Provisional U.S. PatentApplication Ser. No. 61/872,501, filed Aug. 30, 2013, and titled “AUTODRAW FLOW”.

FIELD OF THE INVENTION

Embodiments of the invention generally pertain to the field ofdatabases, and more specifically to techniques for generating, based ondata obtained from a database, a visual flow that illustrates the mannerin which the statuses of objects in a system change over time.

BACKGROUND OF THE INVENTION

People within a business organization often store their data in arelational database. Data stored in a relational database can beorganized into multiple tables having different table names. Each suchtable can include multiple columns and rows. The columns typicallyrepresent some attribute of the data. The rows typically represententities that possess those attributes. The intersections of the columnsand tables are cells that contain values. In a particular rowrepresenting a particular entity and in a particular column representinga particular attribute, a particular cell may contain a value of thatparticular attribute for that particular entity. For example, a columnof a table can indicate different statuses of bugs detected during asoftware development cycle. In the context of software bugs, thesestatuses might include “open,” “awaiting verification,” “fixed,” etc.Other columns might represent other attributes, such as a comment or adescription pertaining to the bugs, or an identity of a software testerwho discovered the bug. Different rows of a table can represent recordsfor different bugs discovered during software testing. The cells in aparticular row can contain the values of the attributes for a particularbug. Assuming that a particular column represents a status, the cells inthose columns might contain numbers that represent the various statusesthat a bug can have.

People within a business organization may be interested in knowing howobjects tend to flow through different statuses that those objects canpossess during their lifetimes. For example, software developers andtesters may be interested in knowing how discovered bugs tend to flowfrom “open” to “awaiting verification” to “fixed” status. Softwaredevelopers and testers may be interested in knowing, at any given momentin history, and for each status, how many bugs possessed that status.Such information can help these people to address possibleinefficiencies in the software development and testing process. Peoplemay be interested in knowing about status flows for a variety ofdifferent objects. For example, in the context of a product ordersystem, people may be interested in knowing the flow of product ordersthrough statuses such as “shipped,” “in transit,” “lost,” “arrived,”“complete,” etc. Different kinds of objects can have different kinds ofstatuses at different times. Different kinds of objects therefore canfollow different status flows.

BRIEF SUMMARY OF THE INVENTION

Described herein is a technique for recommending statuses for inclusionwithin a workflow. A separate score can be generated for each data setof a plurality of data sets, such as a plurality of columns within aplurality of relational tables within a database. The data sets of theplurality of data sets can be ranked based on the scores generated forthe data sets. The ranked data sets can be displayed. User inputselecting a subset of the ranked data sets can be received. The workflowcan be generated based at least in part on the data sets contained inthe subset. For each data set contained in the subset, a separate statusbubble, which corresponds to a status that an object can possess, can beadded to the workflow.

Generating the score for each data set can involve generating a datatype score based at least in part on a type of data that is stored inthe data set and a maximum length of data that can be stored in the dataset. Generating the score for each data set can involve generating adistinct value score based at least in part on a quantity of distinctvalues that are stored in the data set and a total quantity of valuesthat are stored in the data set. Generating the score for each data setcan involve generating a query usage score based at least in part on aquantity of historical queries having a SELECT list that includes thedata set, a quantity of historical queries having a WHERE clause thatincludes the data set, a quantity of historical queries having a GROUPBYclause that includes the data set, and a quantity of historical querieshaving an ORDERBY clause that includes the data set. Generating thescore for each data set can involve generating a name score based atleast in part on whether a name of the data set contains one or morewords from a specified set of words.

Described herein is a technique for interactively displaying statuses ina workflow. A set of statuses in the workflow can be identified from adatabase. For each particular status of the statuses, a first quantityof objects possessing the particular status at a first point in time canbe determined from the database. A graphical element for each particularstatus of the statuses can be rendered. Each graphical element cancontain an indication of the first quantity of objects for thatparticular status. User input can be received. In response to thereceipt of the user input, for each particular status of the statuses, asecond quantity of items possessing the particular status at a secondpoint in time can be determined from the database. The graphical elementfor each particular status of the statuses can be adjusted to cause eachgraphical element to indicate the second quantity of objects possessingthe particular status. Within the rendered workflow, the size of eachgraphical element can depend on a quantity of objects possessing astatus corresponding to that graphical element. Additional statuses canbe added to the workflow. Snapshots of the database can be automaticallygenerated for each of several points in time. The snapshots can beautomatically stored within a data warehouse that is separate from thedatabase.

Described herein is a technique for displaying flows within a workflow.A set of statuses of the workflow can be determined from a database. Afirst quantity of objects possessing each of the statuses at a firstpoint in time can be determined from the database. A second quantity ofobjects possessing each of the statuses at a second point in time can bedetermined from the database. A difference between the first and secondquantities can be calculated for each of the statuses. A probablequantity of objects that flow between two statuses can be estimatedbased on the difference. A graphical element that indicates the probablequantity of objects that flow between the two statuses can be rendered.The graphical element can be a directional pipe that indicates flow ofobject status from a source status to a destination status over time.

Described herein is a technique for automatically rendering a flowdiagram. User input that specifies a key status can be received. Anetwork of relationships between the key status and one or more otherstatuses can be generated. Flows for connections between the statuses inthe network can be determined based on quantities of objects that flowedbetween the statuses in the network during a specified time period. Theconnections can be ranked based on flows determined for the connections.A subset of the ranked connections can be selected. A critical path canbe determined based on the subset of the ranked connections. A flowdiagram including the critical path can be rendered. User input thatrequests increase in zoom can be received. The flow diagram can bere-rendered at a different zoom level than a zoom level at which theflow diagram had been rendered in response to the receipt of the userinput.

The network of relationships can be generated in the following manner.User input specifying the time period can be received. Data pertainingto points in time during the specified time period can be gathered fromsnapshots. For each particular status in a set of selected statuses thatinitially includes only the key status, both a first set of otherstatuses objects possessed prior to assuming the particular status and asecond set of other statuses objects assumed after possessing theparticular status can be determined based on the snapshots. Adetermination can be made whether a current zoom level is equal to atarget zoom level. The current zoom level can be incremented in responseto determining that the current zoom level is not equal to the targetzoom level. At least some of the first and second sets of statuses canbe included in a revised set of selected statuses. The first and secondsets can be re-determined based on the revised set of selected statuses.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram that illustrates a technique for automaticallydetermining a set of candidate statuses for a status flow based on datastored in relational tables, according to an embodiment of theinvention.

FIG. 2 is a flow diagram that illustrates a technique for refining a setof flow fields based on user-selected columns, according to anembodiment of the invention.

FIG. 3 is a flow diagram that illustrates a technique for receiving auser selection of flow fields from a set of columns filtered based onuser-specified criteria, according to an embodiment of the invention.

FIG. 4 is a flow diagram that illustrates a technique for generating anddisplaying a flow including status bubbles representing counts ofobjects having corresponding statuses at a user-specified time,according to an embodiment of the invention.

FIG. 5 is a flow diagram that illustrates a technique for determining aquantity of objects that changed status from a specified source statusto a specified destination status, according to an embodiment of theinvention.

FIG. 6 is a flow diagram illustrating a high-level overview of atechnique for automatically generating and visually rendering a flow ofstatuses of objects in a system, according to an embodiment of theinvention.

FIG. 7 is a flow diagram illustrating a technique for automaticallygenerating a network of statuses that are directly connected with aspecified key status, according to an embodiment of the invention.

FIG. 8 is a flow diagram illustrating an example of a technique forautomatically determining a critical path within a network ofinterconnected statuses, according to an embodiment of the invention.

FIG. 9 depicts a simplified diagram of a distributed system forimplementing one of the embodiments.

FIG. 10 is a simplified block diagram of components of a systemenvironment by which services provided by the components of anembodiment system may be offered as cloud services, in accordance withan embodiment of the present disclosure.

FIG. 11 shows an example of a user interface through which a user canspecify a database that a computing device is to search for columns thatare most likely to represent object status, according to an embodimentof the invention.

FIG. 12 shows an example of a user interface through which a user canview distinct values from a user-selected relational column in adatabase, according to an embodiment of the invention.

FIG. 13 shows an example of a user interface in which several candidatestatus bubbles have been removed in response to the user's selection ofthose bubbles, according to an embodiment of the invention.

FIG. 14 shows an example of a user interface in which some candidatestatus bubbles have been merged together as a result of the userdragging those candidate status bubbles onto other candidate statusbubbles, according to an embodiment of the invention.

FIG. 15 shows an example of a user interface to which some directionalflow pipes have been added to connection some status bubbles with otherstatus bubbles, according to an embodiment of the invention.

FIG. 16 is an example of a user interface in which an alert graphic(shown as a gear) has been placed next to a particular directional flowpipe to signify that a user-specified alert is associated with thatpipe, according to an embodiment of the invention.

FIG. 17 is an example of a user interface displaying an example flowdiagram for a bug resolution process, according to an embodiment of theinvention.

FIG. 18 is another example of a user interface displaying an exampleflow diagram for a bug resolution process, according to an embodiment ofthe invention.

FIG. 19 is an example of a user interface in which a user is dragging acurrent time point to a new position on a displayed timeline, accordingto an embodiment of the invention.

FIG. 20 is an example of a user interface in which a user is selectingan earlier point on the displayed timeline, according to an embodimentof the invention.

FIG. 21 is an example of a user interface showing the state of the flowdiagram at an earlier point in time, according to an embodiment of theinvention.

FIG. 22 is an example of a user interface showing a user's activation ofa portion of the user interface that causes an annotation entrymechanism to appear on the user interface, according to an embodiment ofthe invention.

FIG. 23 is an example of a user interface containing an annotation entrymechanism, according to an embodiment of the invention.

FIG. 24 is an example of a user interface in which an annotation hasbeen added to the current time point in the flow's history, according toan embodiment of the invention.

FIG. 25 illustrates an example of a computer system in which variousembodiments of the present invention may be implemented.

DETAILED DESCRIPTION OF THE INVENTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofembodiments of the invention. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive.

Systems depicted in some of the figures may be provided in variousconfigurations. In some embodiments, the systems may be configured as adistributed system where one or more components of the system aredistributed across one or more networks in a cloud computing system.

In one embodiment of the invention, a computing device can generate anddisplay a visual representation of a status flow of the kind discussedabove. Under one approach, the generation of the status flow to bedisplayed can be accomplished largely through a user's interaction withthe device. For example, according to one approach, a user can instructthe device what the various statuses in a flow are to be. Each of thesestatuses can be represented as a circle or bubble in the flow, forexample. By dragging his finger across the device's touchscreen display,the user can cause the device to place each status bubble in a desiredlocation on the display. The user can direct the device to add aspecified title to each status that the device can then display withinthat status' bubble. The user can then interact with the device toindicate how object flow between these status bubbles. For example,under one approach, a user can drag his finger across a touchscreen fromone bubble to another in order to instruct the device to draw anarrow-like directional “pipe” from the first bubble to the secondbubble, thereby illustrating the flow of objects from the first statusto the second status. Such an approach for generating a visual depictionof a flow can be appropriate under circumstances where the user isalready largely familiar with the system to which the flow applies. Ifthe user already has a firm notion of the various statuses that objectsin the system can possess and the way that those objects' statuseschange within the system, then the largely manual but device-assistedapproach discussed above can be appropriate.

Flow Fields

Under some circumstances, a user desiring to generate a status flowmight not be very familiar with the system for which that status flow isto be generated. Such a user might not be familiar with all of thepossible statuses than an object might possess at any given time. Such auser might not be familiar with the set of other statuses that an objectpossessing a particular status can assume directly after possessing thatparticular status. Without such familiarity, the user might find itdifficult to instruct the device what the flow's status bubbles are tobe and where they are to be located relative to each other within theflow. The user might find it difficult to determine how the directionalpipes linking these bubbles are to be placed within the flow.

Therefore, according to an embodiment of the invention, adevice-assisted technique can automatically determine status candidatesfor which there are potentially to be status bubbles in the flow. Thedevice can perform this technique automatically based on data stored ina relational database, for example, although embodiments of theinvention are not limited to databases. In alternative embodiments ofthe invention, the device can similarly perform the technique based onunstructured data. Following one embodiment of the technique, the devicecan automatically examine the columns within the database's relationaltables in order to determine a set of status candidates to present tothe user. These status candidates correspond to the columns that thedevice determines are most likely to indicate statuses for objects whosedata are stored in the tables. The user can then select, from the set ofstatus candidates, a subset of statuses that are to be represented asstatus bubbles within the flow. The columns that the device determinesare most likely to indicate statuses are called “flow fields.” Althoughthe user might not be able to tell from the relational data alone whichcolumns are likely to indicate object status, by following thetechnique, the computing device can automatically attempt to choosecolumns that probably do indicate object status.

FIG. 1 is a flow diagram that illustrates a technique for automaticallydetermining a set of candidate statuses for a status flow based on datastored in relational tables, according to an embodiment of theinvention. In block 102, a computing device, such as a tablet having atouchscreen display, receives, from a user, user input that specifies adatabase, for example, although embodiments of the invention are notlimited to databases. In alternative embodiments of the invention, thedevice can similarly receive user input that specifies unstructureddata. In block 104, the device begins to examine each column of eachtable in the specified database (or other data source). In block 106,the device determines whether there are any columns in the specifieddatabase (or other data source) that the device has not yet examined. Ifso, then control passes to block 108. Otherwise, control passes to block134.

In block 108, the device sets the current column to be the next columnthat the device has not yet examined. In block 110, the device generatesa data type score for the current column based on the data type of thecurrent column (e.g., number, varchar, etc.) and the maximum length ofthe data that can be stored in the current column. In one embodiment,the data type score for columns potentially representing object statuscan range from 0 to 100. In one embodiment, certain data types, such asBoolean, binary, BLOB (binary large object) and non-whole numbers,produce a data type score of −1 for the current column, since these datatypes are highly unlikely to represent object status. In one embodiment,different data types are associated with different numerical weights,and a column having a particular data type receives a data type scorebased on the weight associated with that column's data type. Data typessuch as integer and string can be associated with relatively highweights relative to other data types, since these data types are highlylikely to represent object status. In one embodiment, the data typescore of a column having a string data type increases as the maximumlength of the data that can be stored in the column decreases below aspecified number of characters (e.g., 100 characters), since shorterstrings are more likely to represent object status than longer stringsare.

In block 112, the device determines whether the current column's datatype score exceeds a specified threshold value (e.g., 0). If so, thencontrol passes to block 114. Otherwise, control passes back to block106—under these circumstances, the current column is excluded fromconsideration as a candidate flow field.

In block 114, the device generates a distinct value score for thecurrent column based on how distinct the values in the current columnare. Generally, columns that contain relatively few distinct values thatare frequently repeated are more likely to represent object status thanare columns that contain relatively many distinct values that areinfrequently repeated. In one embodiment, the device generates thecurrent column's distinct value score using the formula (x/y)*100, wherex represents the quantity of distinct values occurring in the currentcolumn, and y represents the quantity of rows or records in the table inwhich the current column exists. Thus, the distinct value score canrepresent a percentage value.

In block 116, the device determines whether the current column'sdistinct value score is no greater than a specified threshold value(e.g., 10%). If so, then control passes to block 118. Otherwise, controlpasses back to block 106—under these circumstances, the current columnis excluded from consideration as a candidate flow field.

In block 118, the device determines whether the user is authorized toaccess a query history of the specified database (or other data source).If so, then control passes to block 120. Otherwise, control passes toblock 130—under these circumstances, the query usage score will not beconsidered as a factor in determining whether the current column shouldbe considered as a candidate flow field.

In block 120, the device adds, to a query usage score for the currentcolumn, a quantity of historical queries having a SELECT list thatincludes the current column. In block 122, the device adds, to the queryusage score for the current column, a quantity of historical querieshaving a WHERE clause that includes the current column. In block 124,the device adds, to the query usage score for the current column, aquantity of historical queries having a GROUPBY clause that includes thecurrent column. In block 126, the device adds, to the query usage scorefor the current column, a quantity of historical queries having anORDERBY clause that includes the current column.

In block 130, the device generates a column name score for the currentcolumn based on whether the current column's name contains a word withina specified set of words. For example, the specified set of words mightinclude status-suggesting words such as “state,” “status,” “code,” etc.In one embodiment, columns containing at least one words within thespecified set receive a relatively high column name score, while columnsnot containing any words within the specified set receive a relative lowcolumn name score.

In block 132, the device generates a total score for the current columnbased on the data type score, distinct value score, query usage score(if it was generated for the current column), and column name score forthe current column. In one embodiment, different ones of these scorescan be weighted differently and have different amounts of influence onthe computation of the current column's total score. Control passes backto block 106.

Alternatively, in block 134, the device ranks the columns in thespecified database (or other data source) according to their totalscores determined in block 132. In block 136, the device displays atleast a subset of the highest-ranking columns to the user. In oneembodiment, the subset includes only the top X ranked columns, where Xis some specified number or some specified percentage of the quantity ofcolumns in the specified database (or other data source).

In one embodiment, the device can display all of the specifieddatabase's columns to the user, along with an indication for each columnof whether or how likely it is (based on the column's total score orranking) that the column represents object status. In one embodiment,the device can modify the column names for presentation to the user byformatting the column names to make the column names morehuman-readable. Such formatting can include the conversion of underlinecharacters to space characters, for example. Thus, the device presents,to the user, a recommended set of candidate statuses for the flow thatthe user will generate. In one embodiment, the user can then selectcertain candidate statuses to be used as status bubbles within the flow.

In one embodiment, following the device's presentation of therecommended set of candidate statuses to the user, the device canreceive further input from the user to refine the set of flow fieldsthat will be used in the flow. FIG. 2 is a flow diagram that illustratesa technique for refining a set of flow fields based on user-selectedcolumns, according to an embodiment of the invention. In block 202, thedevice presents a set of column names to the user. For example, thedevice can present the set of names of recommended columns as discussedabove in block 136 of FIG. 1. In block 204, the device receives, fromthe user, user input that selects a column name from the set of columnnames. In block 206, the device displays a status set that includesseparate statuses for at least some distinct values contained in theparticular column having the selected column name. In one embodiment,the status set can include a separate status for each such distinctvalue. Each such status can include a status name, which initially maybe the distinct value itself, and also a count of the quantity of rowsthat contain that distinct value in the particular column. In oneembodiment, the user can instruct the device to modify the status nameto a user-specified status name. In one embodiment, the device displaysthe statuses from the set in an order that is based on the quantity ofrows that contain that distinct value in the particular column, suchthat statuses having the largest quantities of rows appear foremost in adisplayed status list.

In block 208, the device receives, from the user, user input thatselects one or more statuses from the displayed status set. In block210, the device removes the selected statuses from the displayed statusset.

In block 212, the device receives, from the user, user input that mergestwo or more statuses from the displayed status set with each other. Forexample, the user input can take the form of a touchscreen gesture thatdrags one status from the displayed status set into another status fromthe displayed status set, thereby indicating to the device that thosestatus sets are to be merged into a single combined status. In block214, the device replaces the two or more statuses with a single combinedstatus. In one embodiment, the user can instruct the device to modifythe status name of the resulting combined status to a user-specifiedstatus name. In one embodiment, the device adds the counts of thequantities of rows that contain the any of the merged statuses' distinctvalues in the particular column, and displays the sum as the count forthe resulting combined status. The operations of blocks 212 and 214 canbe repeated multiple times. The remaining statuses in the displayed setcan be those that ultimately will be included as status bubbles in theflow. In one embodiment of the invention, the merging of statuses asdiscussed above is triggered by the user dragging, from one region ofthe user interface into a flow region of the user interface in which anexisting flow is being generated, a candidate status directly onto anexisting status bubble with which the candidate status is to be merged.

Potentially, a user may have some familiarity with the data that isstored in the database (or other data source), and this familiarity canhelp the user to select some additional columns, or distinct valuescontained therein, as status bubbles in the flow. These selectedcolumns, or selected distinct values within such columns, can be addedto the set of statuses that already have been selected to be statusbubbles in the flow using previously described techniques. FIG. 3 is aflow diagram that illustrates a technique for receiving a user selectionof flow fields from a set of columns filtered based on user-specifiedcriteria, according to an embodiment of the invention. In block 302, thedevice receives, from the user, user input specifying a word and/orpattern. The pattern can include normal characters and wildcardcharacters to be matched, for example. In block 304, the devicereceives, from the user, user input specifying additional criteria. Forexample, the additional criteria can specify that only columns thatcontain primary keys are to be returned. For another example, theadditional criteria can specify that only columns that have a specifieddata type are to be returned. For another example, the additionalcriteria can specify that only columns that store data conforming to aspecified minimum or specified maximum size are to be returned. Foranother example, the additional criteria can specify that only columnsthat contain values that are used as join keys in join operationsinvolving multiple tables are to be returned.

In block 306, the device selects, from all of the columns in all of thetables in a specified database (e.g., the database specified in block102 of FIG. 1), a subset of columns that both (a) have column names thatcontain the user-specified word or that match the user-specified patternand (b) satisfy the additional user-specified criteria. As mentionedabove, embodiments of the invention are not limited to databases. Inalternative embodiments of the invention, the device can similarlyperform the technique based on unstructured data. In block 308, thedevice displays names of the selected columns to the user. In oneembodiment, in response to a user's instruction to do so, the devicedisplays one or more values contained within user-selected columns fromthe selected columns. This information can assist the user indetermining whether those columns actually do represent object status.The technique discussed above in connection with FIG. 2 can then beperformed relative to the names of the selected columns in order toselect certain distinct values (representative of statuses) to beincluded as additional status bubbles to be included in the flow.

In one embodiment of the inventions, the device also enables users togenerate derived statuses that are not directly reflected by any singlecolumn in the database (or other data source). This feature beneficiallyeliminates the need for the database schema to be modified to includecolumns that would serve as a basis for such statuses. In an embodiment,the device includes an interface that receives user input that specifiesone or more (e.g., two) columns and distinct values contained in thoseone or more columns. The user input can also specify a logical operatorsuch as AND or OR. The user input can also specify equality andinequality operators. The device can then generate a new derived statusthat is associated with the columns, distinct values, logical operators(if any), and equality or inequality operators (if any). The device canprovide a user interface through which such a derived status can bestored and used as a flow field or status bubble in a flow in a mannersimilar to other non-derived statuses discussed above. In an embodiment,for both derived and non-derived fields, the device can provide a userinterface through which the name of a status automatically obtained froma column name or from a distinct value in a column can be modified to auser-specified name and persistently stored in association with thecorresponding status bubble.

Thus, discussed above are techniques whereby a computing device canrecommend candidate statuses to users for including in a flow. Thetechniques can make use of information contained in the database (orother data source) in order to attempt, automatically, to estimate whichcolumns are likely to contain status data. A user can then selectcertain of the recommended candidate statuses and place correspondingstatus bubbles within the flow. In one embodiment, this is accomplishedthrough a user interface that the user uses to drag a recommendedcandidate status from one region of the user interface to a flow regionof the user interface, at which point the status bubble becomes a partof the flow. In one embodiment, the candidate statuses also include ageneric “start” status that the user can initially drag into the flowregion of the user interface to being creating the flow. As is discussedabove, in one embodiment, a recommended candidate status can be mergedwith an existing status bubble in the flow in response to therecommended candidate status being dragged onto the existing statusbubble.

While or after the user has placed status bubbles in the flow, the usercan link these statuses together with arrow-like directional pipes. Inan embodiment, this linkage is accomplished through dragging gestureagainst the device's touchscreen, from a source status bubble to adestination status bubble. In another embodiment, this linkage isaccomplished automatically when the user drags a candidate status intothe flow region of the user interface. In such an embodiment, the devicecan automatically link the new status bubble as a destination statusbubble with a directional pipe originating from a source status bubbleto which the new status bubble is closest in the flow region of the userinterface. Once the directional pipe has been placed in either manner,the device can use historical database data (or historical data fromsome other data source) to generate data that indicates how objects haveflowed, over time, from the source status to the destination status.This data can be generated through a series of temporally-spaceddatabase snapshots spanning some specified historical period. In oneembodiment, the device presents, next to each directional pipe, agraphic that represents this data. In one embodiment, the graphic cantake the form of a two-dimensional bar chart or line graph, in which oneaxis represents discrete time intervals and the other axis representsthe quantity of objects that changed status from the source status tothe destination status during the corresponding time interval.

In one embodiment, each status bubble additionally contains a graphicsuch as a two-dimensional bar chart or line graph that represents howthe status bubble's object count changes over time; one axis canrepresent time and the other axis can represent the quantity of objectshaving the bubble's status at that time.

Flow State Totals

In one embodiment, in addition to the flow diagram, including statusbubbles and directional pipes linking those status bubbles as discussedabove, the user interface can include a timeline that can be manipulatedthrough user input. The timeline can be at virtually any scale, coveringa span of minutes or a span of months or some other time frame. The userinterface can receive user input that selects a specified point upon thetimeline. In response to such a selection, the device can transition thedisplay of the flow diagram to represent a state of the database (orother data source) at a moment in time corresponding to the selectedpoint. At the selected moment in time, various objects represented inthe database (or other data source) can possess various ones of thestatuses reflected by the flow's status bubbles.

In an embodiment, the device's transition of the display involves thedevice's calculation, for each status bubble in the flow, of thequantity of objects in the database (or other data source) thatpossessed that status' bubbles corresponding status. In transitioningthe display, the device can update, in each displayed status bubble inthe flow, the displayed count of objects that possessed that bubble'sstatus at the selected point in time. Furthermore, in one embodiment,the device can additionally re-size each status bubble in the flowproportionately to the object count contained within that status bubble;status bubbles having larger counts can be sized larger than statusbubbles having smaller counts. As the device receives user instructionsto transition the display of the flow to different points in time in themanner described above, the device can modify the object counts andsizes for each status bubble accordingly.

In one embodiment, the user interface additionally includesuser-selectable controls for playing or pausing an animated slideshow ofthe states of the flow at progressing points in time. The device'sreceipt of a user input that selects the play control causes the deviceto animate the transition of the flow state display gradually butcontinuously from the selected point on the timeline toward the endthereof. Thus, a user can watch as certain status bubbles grow or shrinkas objects flow between their corresponding statuses over time. In anembodiment, while viewing a particular state of the flow using thistechnique, a user can optionally add an annotation that refers to theparticular state as a whole. The device can store this annotation inassociation with the time point corresponding to the flow state that wasbeing viewed at the time that the annotation was made—the flow state towhich the annotation refers. Later, when the same or other user viewthis particular flow state (e.g., using the timeline control), thedevice can present the annotation along with the particular flow stateso that such users benefit from the knowledge contained therein.

According to an embodiment of the invention, the database (or other datasource) periodically stores snapshots of at least some tables in thedatabase. For example, the database can periodically store snapshots ofeach table that contains a column for which there is a correspondingstatus bubble in the flow. The database can generate a snapshot at theend of each time interval having a specified duration. The device canaccess these snapshots in order to generate and display the flow as itwould have existed at a user-specified time.

FIG. 4 is a flow diagram that illustrates a technique for generating anddisplaying a flow including status bubbles representing counts ofobjects having corresponding statuses at a user-specified time,according to an embodiment of the invention. In block 402, the devicereceives user input that specifies a point in time. For example, using atouchscreen interface of a tablet computing device, a user can select,on a timeline presented on a user interface along with the flow, aparticular point in time. In response to the receipt of this user input,the device can reposition, on the timeline, a marker that indicates thatthe selected point in time is the current temporal position at which thestate of the flow is to be shown.

In block 404, the device queries a database to retrieve a snapshot of atleast a portion of the database that corresponds to the selected pointin time, for example, although embodiments of the invention are notlimited to databases. In alternative embodiments of the invention, thedevice can similarly perform the technique based on unstructured data.The device can query for the closest snapshot available, time-wise, ifno snapshot exists for the exact time point selected. The database canbe stored remotely from the device. The database (or other data source)can even be stored in a cloud computing environment. Under suchcircumstances, the database can take the form of a service that is notowned by the user, but may be accessed by multiple users over networksremotely. The query can be narrowed such that only status data (i.e.,certain columns) pertaining to the status bubbles in the flow areselected by the query. Data pertaining to other snapshots are notqueried.

In block 406, for each status bubble in the flow diagram, the devicedetermines a quantity of rows from the query results that contain thedistinct value that corresponds to that status bubble. Thus, the devicecan determine, for each status bubble, a quantity of objects thatpossessed that bubble's status at the selected time point. In block 408,for each status bubble in the flow diagram, the device determines a sizefor that status bubble. In one embodiment, each status bubble's radiusis calculated by multiplying or dividing that status bubble's quantityof objects by some specified value. In block 410, for each statusbubble, the device re-draws that status bubble with its new size and itsnew object count as of the selected time point.

The technique shown in FIG. 4 can be performed multiple times. Thetechnique can be performed each time that the device receives user inputspecifying a different time point on the timeline. After displaying theflow with status bubbles containing object counts as of a first point intime, the device can receive user input specifying a second point intime. In response, the device can display the flow with status bubblescontaining objects counts as of the second point in time. Thus, eachstatus bubble in the flow can contain a count of the quantity of objectsthat possessed that bubble's status at a specified moment, and eachstatus bubble's size can be scaled to be proportionate to the objectcount contained within that status bubble.

Auto Flow Warehousing

As is discussed above, in order to show representations of the flow atdifferent points in time, a database (or other data source) can storesnapshots of its state—or the state of specified portions thereof—atvarious time points. In one embodiment of the invention, the databaseitself does not maintain these snapshots. Instead, in an embodiment ofthe invention, the database periodically performs a back-up operationthat generates the snapshot, and this snapshot is then moved from thedatabase to an external data warehouse where the snapshot ispersistently stored. In such an embodiment, when the device queries fora particular snapshot pertaining to a specified moment in time, thedevice can query the data stored in the data warehouse instead of thedata stored in the database.

In one embodiment of the invention, in order to reduce the size of thedata stored in the warehouse and the time required to generate and movethe back-up data, a tool is provided whereby a user can specify which ofthe database's tables are to be involved in the back-up operation. Forexample, a user can choose, from all of the tables in the database, justthe tables that include columns that contain object status data. As aresult of this selection, the back-up operation will only create a copyof the data from the selected tables, and a smaller volume of data willbe communicated to and stored at the data warehouse during each temporalinterval. Alternatively, using a technique similar to that discussedabove in connection with FIG. 1, a tool can attempt to determineautomatically which of the database's columns are most likely to storeobject status. An automated software agent, potentially executing on thesame system that contains the database, can then use this determinationto periodically perform a back-up operation of just the tables thatcontain those columns.

Flow Pipe Totals

As is discussed above, in an embodiment of the invention, directionalpipes can be added to a flow linking status bubbles and illustrating thedirection in which objects flow in a system from one status to another.Each pipe can serve as an indication that one or more objects changedstatus from the status of the source status bubble to the status of thedestination status bubble. There are numerous ways in which thesedirectional pipes can be added to the flow. The directional pipes can beadded in response to a user performing a dragging gesture across atouchscreen from a source status bubble to a destination status bubble.

The directional pipes can be added automatically in response to a userdragging a recommended candidate status into a flow region of a userinterface, connecting the new status bubble with a closest existingstatus bubble as a destination-source pair. Other techniques forautomatically generating a flow are also discussed below.

Also as is discussed briefly above, in an embodiment of the invention,the device displays a graphic next to each directional pipe. The graphicillustrates a quantity of objects that flowed along the directional pipefrom the source status bubble to the destination status bubble duringeach time interval in a series of multiple time intervals. The graphiccan take the form of a two-dimensional bar chart or line graph in whichone axis represents the time intervals and the other axis represents thequantity of objects that flowed through the directional pipe (i.e.,changed status from the source status bubble's status to the destinationstatus bubble's status) during particular time intervals. In order togenerate such a graphic, in an embodiment of the invention, the deviceperforms a technique to determine, for each such time interval, thequantity of objects that changed status in this manner. The techniquecan use historical database snapshots, discussed above, in order to makethis determination, for example, although embodiments of the inventionare not limited to databases. In alternative embodiments of theinvention, the device can similarly perform the technique based onunstructured data. The snapshots can include a separate snapshot foreach time point in a series of time points.

FIG. 5 is a flow diagram that illustrates a technique for determining aquantity of objects that changed status from a specified source statusto a specified destination status, according to an embodiment of theinvention. In block 502, a computing device sets a first time point in aseries of time points to be the current time point. In block 504, thedevice queries a snapshot corresponding to the current time point toselect rows that contain the source status bubble's distinct value inthe column corresponding to the source status bubble. In block 506, thedevice selects, from the series of time points, a subsequent time pointthat is a specified temporal distance later than the current time point.This temporal distance can be user-specified or otherwise configured,depending on the desired granularity of information. In block 508, thedevice queries a snapshot corresponding to the subsequent time point toselect rows that contain the destination status bubble's distinct valuein the column corresponding to the destination status bubble. It ispossible that not all of the objects that flowed from the source statusbubble flowed to the destination status bubble; if the source statusbubble is linked by directional pipes to multiple destination bubbles,then it is possible that some of the objects that flowed from the sourcestatus bubble might have flowed to status bubbles other than thedestination status bubble. In block 510, using unique object identifiers(e.g., bug identifiers) specified within the rows returned by thequeries of blocks 506 and 508, the device performs a join of the queryresults in order to obtain a set of rows for objects that wererepresented in both sets of query results—the intersection of the resultsets based on unique object identifier. The result of the join is theset of objects that possessed the source status bubble's status as ofthe current time point but possessed the destination status bubble'sstatus as of the subsequent time point, indicating that these objectschanged status from the source status to the destination status in thetemporal interval occurring between the first and subsequent timepoints. In block 512, the device determines the quantity of objectsreturned by the join operation. In block 514, the device stores thisquantity as the number of objects that flowed from the source statusbubble to the destination status bubble during the temporal intervaloccurring between the first and subsequent time points. In block 516,the device determines whether any snapshots for a time point occurringlater than the subsequent time point exist. If so, then control passesto block 518. Otherwise, the technique illustrated in FIG. 5 concludes.

In block 518, the device sets the current time point to be thesubsequent time point that was selected in block 506. Control passesback to block 504. After the technique of FIG. 5 concludes, the devicecan use the object quantities determined and stored for each timeinterval to generate the graphic that illustrates how objects flowedthrough the directional pipe over time.

Auto Draw Flow

As is discussed above, one technique for generating a flow involves auser selecting device-recommended statuses and dragging those statusesinto a flow region of a user interface, and potentially supplementingthose statuses with additional statuses selected by user query and/orderived by user specifications. Various techniques, also discussedabove, exist for linking status bubbles together with directional pipesin the flow region of the user interface.

Discussed below is a technique wherein a flow can be generated in a moreautomated manner. Using this technique, a user is not required to decidewhich statuses ought to be included the flow. Instead, using thistechnique, the device can automatically attempt to determine the mostsignificant statuses in the system, and include those statuses in theflow. Additionally, using this technique, a user is not required todesign the on-screen layout of the flow in the flow region of the userinterface. Instead, using this technique, a device can attempt to ensurethat the most important or interesting parts of a flow will bepositioned centrally within the flow region, ideally so that as much ofthe flow as possible will be visible at once, but in any case so thatscrolling is only required to view less significant portions of theflow. Beneficially, use of this technique avoids a need for the user tohave a high familiarity with the statuses that objects in the system canassume or with the manner in which those statuses tend to change in thesystem. Use of this technique can allow users to visualize parts offlows whose existence those users might not have otherwise considered ontheir own.

According to one embodiment of the invention, flows can be automaticallygenerated and drawn using the technique at different levels ofrefinement or “zoom.” In an embodiment, the level of refinement at whichthe flow will be automatically generated and drawn using this techniquecan be user-specified. Such a level of refinement can involve twodifferent dimensions, which can be separately specified: first, networkdepth, which can affect the length of chains of connected status bubblesthat will be included in the flow; and second, detail, which can affectthe threshold at which connections (i.e., directional pipes) betweenbubbles are deemed to be significant enough, based on the quantity ofobjects flowing along those connections, to be included in the flow.

FIG. 6 is a flow diagram illustrating a high-level overview of atechnique for automatically generating and visually rendering a flow ofstatuses of objects in a system, according to an embodiment of theinvention. In block 602, the device receives user input specifying a keystatus. In an embodiment, the device can present a list of possibleobject statuses to the user (e.g., using a technique similar to thatdescribed above in connection with FIG. 1), and the user can select thekey status from that list. In block 604, the device receives user inputcommanding the device to automatically draw a flow based on the keystatus. For example, the user can give the command by activating, in auser interface, a button labeled “auto draw flow.” In block 606, thedevice generates a network of relationships between the key status andone or more other statuses. This generation is described in greaterdetail in connection with FIG. 7 below. In block 608, the devicedetermines flows for the connections between the networked statusesdetermined in block 606. For each connection between the networkedstatuses, a quantity of objects that flowed through that connectionduring a specified time period (e.g., the time period specified in block704 of FIG. 7) is determined. This quantity becomes the “flow” for thatconnection. The flow for a connection may be determined using atechnique similar to that discussed above in connection with FIG. 5, forexample.

In block 610, the device ranks the connections based on their flow. Inblock 612, the device uses the ranking of block 610 to select, from allof the connections, the top X connections ranked by flow, where X isuser-configurable. X can be a specified quantity or a specifiedpercentage. In one embodiment, the device can select at least aspecified minimum quantity of connections if the size of the set of topX connections is not at least this minimum quantity. In block 614, thedevice determines a critical path based on at least some of the top Xconnections. This determination is described in greater detail inconnection with FIG. 8 below. In block 616, the device renders anddisplays a flow diagram that includes the critical path. The flowdiagram can be rendered and displayed initially at a specified level ofrefinement or “zoom.” The rendering is described in greater detailbelow. In block 618, the device can receive user input that instructsthe device to increase the detail of the whole flow diagram or aselected status thereof. In block 620, the device re-renders anddisplays the flow diagram at a level of refinement specified by the userinput received in block 618. Control passes back to block 618.

Generating the Network of Relationships

As is discussed above in connection with block 606 of FIG. 6, in oneembodiment, a device generates a network of relationships between thekey status and one or more other statuses. In an embodiment, the devicegenerates a network of (a) all statuses that an object's statushistorically has directly changed to from the key status and (b) allstatuses from which an object's status historically has directly changedto the key status. In other words, the device can determineautomatically the set of all other status bubbles that ought to (basedon recorded past status changes) have directional pipes leading directlyfrom or directly from the status bubble for the key status. Historicaldata can be observed to determine the statuses to which objects havemoved and from which objects have moved in the past.

FIG. 7 is a flow diagram illustrating a technique for automaticallygenerating a network of statuses that are directly connected with aspecified key status, according to an embodiment of the invention. Inblock 702, the device receives user input specifying a key status (as inblock 602 of FIG. 6). In block 704, the device receives user inputspecifying a time period. In block 706, the device queries databasesnapshots to gather data pertaining to time points in the specified timeperiod. Alternatively, the device can analyze snapshot data obtainedfrom some other data source. In block 708, the device initially sets acurrent refinement or “zoom” level to be a value of one. In block 710,the device initializes a set of selected statuses to include only thekey status.

In block 712, the device determines whether the set of selected statusesincludes any statuses that the device has not yet examined. If so, thencontrol passes to block 714. Otherwise, control passes to block 726.

In block 714, the device sets the current status to be a status in theset of selected statuses that the device has not yet examined. In block716, the device determines all statuses from which any object's statuschanged to the current status during the time period specified in block704. In an embodiment, this determination can be accomplished byexamining the data gathered in block 706 and finding all objects thatpossessed some other status immediately prior to possessing the currentstatus. These other statuses are then those determined in block 716. Inblock 718, the device stores data indicating connections from each suchother status to the current status. In block 720, the device determinesall statuses to which any object's status changed from the currentstatus during the time period specified in block 704. In an embodiment,this determination can be accomplished by examining the data gathered inblock 706 and finding all objects that possessed the current statusimmediately prior to possessing some other status. These other statusesare then those determined in block 720. In block 722, the device storesdata indicating connections from the current status to each such otherstatus. In block 724, the device adds, to a set of newly discoveredstatuses, all statuses determined in blocks 716 and 720 that have neverpreviously been within the set of selected statuses. Control passes backto block 712.

Alternatively, in block 726, the device determines whether the currentrefinement or “zoom” level is equal to a specified target refinement or“zoom” level. The target refinement or “zoom” level can beuser-specified or otherwise configured. If the current refinement or“zoom” level is equal to the target refinement or “zoom” level, then thetechnique concludes, having automatically generated a set of significantstatuses and the connections between them. Otherwise, control passes toblock 728.

In block 728, the device moves all statuses from the set of selectedstatuses to an “already processed” status set, keeping track of whichstatuses have been in that set so those statuses will not be added tothe set of newly discovered statuses in the future. In block 730, thedevice adds, to the set of selected statuses, all statuses from the setof newly discovered statuses that are not in the “already processed”status set. In block 732, the device removes all statuses from the setof newly discovered statuses. In block 734, the device increments thecurrent refinement or “zoom” level by one. Control passes back to block712.

Determining the Critical Path

As is discussed above in connection with block 614 of FIG. 6, in oneembodiment, a device determines a critical path based on at least someof the top X flow-ranked connections between statuses. FIG. 8 is a flowdiagram illustrating an example of a technique for automaticallydetermining a critical path within a network of interconnected statuses,according to an embodiment of the invention. In block 802, the deviceadds, to a set of critical directional pipes, the top X flow-rankedconnections determined in block 612 of FIG. 6. In block 804, for eachparticular connection in set of critical directional pipes, the deviceselects, from the set of connections generated for the network in block606, any other connections needed to complete a path from the particularconnection to the key status (specified in block 602 of FIG. 6), if sucha path does not already exist. In block 806, the device adds theconnections selected in block 606 to a set of pseudo-criticaldirectional pipes. As a result of this technique, the set of criticaldirectional pipes contains the connections that form the critical path,and the set of pseudo-critical directional pipes contains connectionsthat provide context to the critical path.

Rendering the Flow Diagram

As is discussed above in connection with block 616 of FIG. 6, in anembodiment, a device can render and display a flow diagram that includesthe critical path determined using the technique discussed above inconnection with FIG. 8. A technique for rendering the flow diagram isdescribed below. The technique operates on a set of principles.According to these principles, the technique attempts to keep thecritical path centered in the user interface. Additionally, thetechnique attempts to keep the status bubble for the key status(specified in block 602 of FIG. 6) centered as much as possible whileconforming to the former principle. The technique attempts to avoid theneed to scroll the user interface to see any portion of the criticalpath. In an embodiment, the technique attempts to lay out the flowdiagram in a manner that reduces vertical scrolling in favor ofhorizontal scrolling if any scrolling is necessary to view any part ofthe flow diagram. In generating the flow diagram, the device can rendereach connection in the sets of critical and pseudo-critical directionalpipes, as well as each status bubble for each status that those pipesinterconnect. Other connections and status bubbles can be omitted fromthe display.

In an embodiment, the device splits the user interface into a virtualgrid. The construction of the virtual grid can be based on configurableparameters such as a maximum resolution for the flow diagram and theminimum size in pixels required for each status bubble. The device caninitially attempt to generate the flow diagram with a generally linearappearance. The device can attempt to generate the flow diagram so thatthe status bubbles connected by the critical directional pipes andpseudo-critical directional pipes occur as much as possible on the samestraight line. After generating the flow diagram in this manner, thedevice can determine whether any part of the flow diagram will extendbeyond the borders of the user interface. If so, to prevent the need forscrolling, the device can bend that part of the flow diagram in aperpendicular direction, so that more of the “real estate” of the userinterface is occupied by the flow diagram.

Leaks

The rendering process discussed above can obscure some details about thenetwork. Some non-critical directional pipes might be omitted from thedisplay of the flow diagram, for example. As a result, the aggregateflows into and out of a particular status bubble might not be perfectlyequal in magnitude; the net of all of the in-flows to out-flows mightnot be zero as displayed. Such a particular status bubble possesses a“leak.” According to an embodiment of the invention, the device candetermine, for each status bubble to be rendered, whether that statusbubble as displayed will possess a leak. For each such status bubble,the device can display, next to that status bubble and in associationwith that status bubble, a graphic element that indicates to a viewerthat the status bubble as shown possesses a leak. The viewer thenbecomes aware of the reason for the discrepancy in in-flows andout-flows relative to the status bubble. The user can elect to “zoom in”on that status bubble in order to see a more detailed version of thatpart of the flow diagram that is less likely to be subject to leaks.

Zoom

As is discussed above, there are two possible ways in which a user canview the flow diagram with greater refinement or “zoom.” First, the usercan instruct the device to generate the status network in a manner thatsearches farther away from the key status when discovering otherstatuses that ought to be added to network based upon which the flowdiagram will be rendered. This kind of zoom can be achieved byincreasing the target refinement or “zoom” level discussed above inconnection with block 726 of FIG. 7. Second, the user can instruct thedevice to include a larger quantity of the connections that areflow-ranked lower than those previously selected for inclusion in theflow diagram, as discussed above in connection with block 612 of FIG. 6.This kind of zoom can be achieved by increasing the value of X discussedin connection with block 612.

In an embodiment, in response to a user's commands, the device canperform either kind of zoom (as specified by the commands) relative tothe whole flow diagram or relative to a user-selected status representedin the flow diagram. In response to such commands, the device canre-generate the status network using revised parameters and canre-render the flow diagram based on the regenerated status network.

Example User Interfaces

FIG. 11 shows an example of a user interface through which a user canspecify a database that a computing device is to search for columns thatare most likely to represent object status, according to an embodimentof the invention. As shown, the user interface is displayed on a tabletcomputing device. The user interface includes a search field. A businessuser interested in a bug fixing process might enter the word “bug” intothe search field. The search results are displayed below the searchfield. The search results include names of several columns from the bugdatabase. The column names include “bug: status.” In this example, acomputing device has automatically identified the “bug: status” columnas potentially representing object status. Consequently, the computingdevice has caused the display, next that that column name, of a linklabeled “analyse flow.” In response to the user's activation of thislink, the tablet computing device can present a user interface such asthe one illustrated in FIG. 12.

FIG. 12 shows an example of a user interface through which a user canview distinct values from a user-selected relational column in adatabase, according to an embodiment of the invention. In response tothe user's activation of the “analyse flow” link next to the “bug:status” column name, the computing device can present, to the user,candidate status bubbles that represent the distinct values found withinthe “bug: status” column. Each candidate status bubble contains a countof the quantity of that bubble's distinct value within the “bug: status”column. The candidate status bubbles can be sorted within the userinterface by this count, from highest to lowest.

In an embodiment, the computing device receives user input that selectsone or more candidate status bubbles to be removed from those thatultimately will be included within the flow diagram to be generated.FIG. 13 shows an example of a user interface in which several candidatestatus bubbles have been removed in response to the user's selection ofthose bubbles, according to an embodiment of the invention. In thisexample, the user has decided that he is only interested in trackingcode bugs, and so the user has selected candidate status bubbles relatedto enhancements—distinct values 16, 97, 98, and 94—anddocumentation—distinct value 99.

As is discussed above, in an embodiment, the computing device receivesuser input that merges two or more candidate status bubbles into asingle unified status bubble. FIG. 14 shows an example of a userinterface in which some candidate status bubbles have been mergedtogether as a result of the user dragging those candidate status bubblesonto other candidate status bubbles, according to an embodiment of theinvention. In this example, the user has decided that some of thecandidate status bubbles are equivalent for the user's purpose, and sohas caused those bubbles to be merged. Additionally, as discussed above,in an embodiment, the statuses that status bubbles represent can bere-named as specified by the user. In this example, the user has causedthe creation of combined status bubbles labeled “awaiting fix” (formerdistinct value 11), “awaiting verification” (merger of former distinctvalues 35 and 80), “fixed” (merger of former distinct values 74, 75, 90,and 93), and “not a bug” (merger of former distinct values 31, 32, 33,36, 91, 92, and 96). The counts of the merged status bubbles are equalto the sum of the counts from the status bubbles merged.

FIG. 15 shows an example of a user interface to which some directionalflow pipes have been added to connection some status bubbles with otherstatus bubbles, according to an embodiment of the invention. The statusbubbles shown are the candidate status bubbles that have been selectedfor inclusion in the flow diagram. As shown in FIG. 15, the user hasdecided that he is interested in seeing the flow from the “awaiting fix”status bubble to the “awaiting verification” status bubble, and the flowfrom the “awaiting verification” status bubble to the “fixed” statusbubble. The user has connected these status bubbles with directionalflow pipes. As is discussed above, in one embodiment, such pipes can beadded through a dragging gesture made against a tablet computingdevice's touchscreen display. In response to the user's addition of thedirectional flow pipes, the computing device has calculated a history offlows between the corresponding statuses based on historical databasesnapshots. Next to each directional flow pipe, the computing device hasdisplayed a two-dimensional line chart graphic showing how flow from thesource status to the destination status has varied over time.

In one embodiment of the invention, in response to a user's command, acomputing device can associate a user-specified action with auser-specified directional flow pipe. FIG. 16 is an example of a userinterface in which an alert graphic (shown as a gear) has been placednext to a particular directional flow pipe to signify that auser-specified alert is associated with that pipe, according to anembodiment of the invention. In this example, the user has instructedthe computing device to associate, with the pipe connecting the“awaiting fix” status bubble to the “awaiting verification” statusbubble, an alert that will be triggered in response to user-specifiedcriteria being satisfied. In this example, the user-specified criteriaare satisfied if the quantity of bugs having the “awaiting fix” statusexceed the quantity of bugs that flowed from the “awaiting fix” statusto the “awaiting verification” status within a most recent week-longtime interval. The alert can be in the form of an e-mail or othermessage to the user. Alternatively, the alert can appear on the userinterface. For example, the directional pipe associated with the alertcan be made to appear in a red color when the criteria are satisfied.Such an alert can inform the user that a dangerously high backlog ofbugs is being built up, which the user might not have the work capacityto reduce.

FIG. 17 is an example of a user interface displaying an example flowdiagram for a bug resolution process, according to an embodiment of theinvention.

FIG. 18 is another example of a user interface displaying an exampleflow diagram for a bug resolution process, according to an embodiment ofthe invention. The status bubbles show counts for the quantities of bugspossessing those bubble's statuses. The statuses of the bugs flow fromthe “open” status to the “awaiting verification status” to the “fixed”status. The sizes of the status bubbles change in proportion to thequantity of bugs possessing those bubble's statuses. The bar chartinside each status bubble shows a history of the count of bugspossessing that bubble's status over time. Next to each directional pipeconnecting the status bubbles is a bar chart showing the historical flowrates between the connected status bubbles. The flow diagram reflectsthe state of the system at a particular time point; in this example, thetime point is Dec. 18, 2012. At this time point, most bugs are fixed,but many are awaiting verification.

FIG. 19 is an example of a user interface in which a user is dragging acurrent time point to a new position on a displayed timeline. Bydragging the current time point to a position representing a previousmoment in time, the user can view the state of the system at an earliertime point, according to an embodiment of the invention.

FIG. 20 is an example of a user interface in which a user is selectingan earlier point on the displayed timeline, according to an embodimentof the invention.

FIG. 21 is an example of a user interface showing the state of the flowdiagram at an earlier point in time, according to an embodiment of theinvention. In mid-September, the count of bugs is shown to rise rapidly.

In one embodiment of the invention, the user interface provided amechanism through which a user can add an annotation to a specific timepoint in the flow's history. FIG. 22 is an example of a user interfaceshowing a user's activation of a portion of the user interface thatcauses an annotation entry mechanism to appear on the user interface,according to an embodiment of the invention.

FIG. 23 is an example of a user interface containing an annotation entrymechanism, according to an embodiment of the invention. As shown, theuser is touching various virtual keys displayed on a virtual keyboard inorder to add an annotation to the current time point in the flow'shistory.

FIG. 24 is an example of a user interface in which an annotation hasbeen added to the current time point in the flow's history, according toan embodiment of the invention. As shown, the explanatory annotation,“Bugs shot up; Branch closed” has been associated with the current timepoint. In an embodiment, this annotation is presented thereafterwhenever the state of the flow diagram at that time point is displayed.

Hardware Overview

FIG. 9 depicts a simplified diagram of a distributed system 900 forimplementing one of the embodiments. In the illustrated embodiment,distributed system 900 includes one or more client computing devices902, 904, 906, and 908, which are configured to execute and operate aclient application such as a web browser, proprietary client (e.g.,Oracle Forms), or the like over one or more network(s) 910. Server 912may be communicatively coupled with remote client computing devices 902,904, 906, and 908 via network 910.

In various embodiments, server 912 may be adapted to run one or moreservices or software applications provided by one or more of thecomponents of the system. In some embodiments, these services may beoffered as web-based or cloud services or under a Software as a Service(SaaS) model to the users of client computing devices 902, 904, 906,and/or 908. Users operating client computing devices 902, 904, 906,and/or 908 may in turn utilize one or more client applications tointeract with server 912 to utilize the services provided by thesecomponents.

In the configuration depicted in the figure, the software components918, 920 and 922 of system 900 are shown as being implemented on server912. In other embodiments, one or more of the components of system 900and/or the services provided by these components may also be implementedby one or more of the client computing devices 902, 904, 906, and/or908. Users operating the client computing devices may then utilize oneor more client applications to use the services provided by thesecomponents. These components may be implemented in hardware, firmware,software, or combinations thereof. It should be appreciated that variousdifferent system configurations are possible, which may be differentfrom distributed system 900. The embodiment shown in the figure is thusone example of a distributed system for implementing an embodimentsystem and is not intended to be limiting.

Client computing devices 902, 904, 906, and/or 908 may be portablehandheld devices (e.g., an iPhone®, cellular telephone, an iPad®,computing tablet, a personal digital assistant (PDA)) or wearabledevices (e.g., a Google Glass® head mounted display), running softwaresuch as Microsoft Windows Mobile®, and/or a variety of mobile operatingsystems such as iOS, Windows Phone, Android, BlackBerry 10, Palm OS, andthe like, and being Internet, e-mail, short message service (SMS),Blackberry®, or other communication protocol enabled. The clientcomputing devices can be general purpose personal computers including,by way of example, personal computers and/or laptop computers runningvarious versions of Microsoft Windows®, Apple Macintosh®, and/or Linuxoperating systems. The client computing devices can be workstationcomputers running any of a variety of commercially-available UNIX® orUNIX-like operating systems, including without limitation the variety ofGNU/Linux operating systems, such as for example, Google Chrome OS.Alternatively, or in addition, client computing devices 902, 904, 906,and 908 may be any other electronic device, such as a thin-clientcomputer, an Internet-enabled gaming system (e.g., a Microsoft Xboxgaming console with or without a Kinect® gesture input device), and/or apersonal messaging device, capable of communicating over network(s) 910.

Although exemplary distributed system 900 is shown with four clientcomputing devices, any number of client computing devices may besupported. Other devices, such as devices with sensors, etc., mayinteract with server 912.

Network(s) 910 in distributed system 900 may be any type of networkfamiliar to those skilled in the art that can support datacommunications using any of a variety of commercially-availableprotocols, including without limitation TCP/IP (transmission controlprotocol/Internet protocol), SNA (systems network architecture), IPX(Internet packet exchange), AppleTalk, and the like. Merely by way ofexample, network(s) 910 can be a local area network (LAN), such as onebased on Ethernet, Token-Ring and/or the like. Network(s) 910 can be awide-area network and the Internet. It can include a virtual network,including without limitation a virtual private network (VPN), anintranet, an extranet, a public switched telephone network (PSTN), aninfra-red network, a wireless network (e.g., a network operating underany of the Institute of Electrical and Electronics (IEEE) 902.11 suiteof protocols, Bluetooth®, and/or any other wireless protocol); and/orany combination of these and/or other networks.

Server 912 may be composed of one or more general purpose computers,specialized server computers (including, by way of example, PC (personalcomputer) servers, UNIX® servers, mid-range servers, mainframecomputers, rack-mounted servers, etc.), server farms, server clusters,or any other appropriate arrangement and/or combination. In variousembodiments, server 912 may be adapted to run one or more services orsoftware applications described in the foregoing disclosure. Forexample, server 912 may correspond to a server for performing processingdescribed above according to an embodiment of the present disclosure.

Server 912 may run an operating system including any of those discussedabove, as well as any commercially available server operating system.Server 912 may also run any of a variety of additional serverapplications and/or mid-tier applications, including HTTP (hypertexttransport protocol) servers, FTP (file transfer protocol) servers, CGI(common gateway interface) servers, JAVA® servers, database servers, andthe like. Exemplary database servers include without limitation thosecommercially available from Oracle, Microsoft, Sybase, IBM(International Business Machines), and the like.

In some implementations, server 912 may include one or more applicationsto analyze and consolidate data feeds and/or event updates received fromusers of client computing devices 902, 904, 906, and 908. As an example,data feeds and/or event updates may include, but are not limited to,Twitter® feeds, Facebook® updates or real-time updates received from oneor more third party information sources and continuous data streams,which may include real-time events related to sensor data applications,financial tickers, network performance measuring tools (e.g., networkmonitoring and traffic management applications), clickstream analysistools, automobile traffic monitoring, and the like. Server 912 may alsoinclude one or more applications to display the data feeds and/orreal-time events via one or more display devices of client computingdevices 902, 904, 906, and 908.

Distributed system 900 may also include one or more databases 914 and916. Databases 914 and 916 may reside in a variety of locations. By wayof example, one or more of databases 914 and 916 may reside on anon-transitory storage medium local to (and/or resident in) server 912.Alternatively, databases 914 and 916 may be remote from server 912 andin communication with server 912 via a network-based or dedicatedconnection. In one set of embodiments, databases 914 and 916 may residein a storage-area network (SAN). Similarly, any necessary files forperforming the functions attributed to server 912 may be stored locallyon server 912 and/or remotely, as appropriate. In one set ofembodiments, databases 914 and 916 may include relational databases,such as databases provided by Oracle, which are adapted to store,update, and retrieve data in response to SQL-formatted commands.

FIG. 10 is a simplified block diagram of one or more components of asystem environment 1000 by which services provided by one or morecomponents of an embodiment system may be offered as cloud services, inaccordance with an embodiment of the present disclosure. In theillustrated embodiment, system environment 1000 includes one or moreclient computing devices 1004, 1006, and 1008 that may be used by usersto interact with a cloud infrastructure system 1002 that provides cloudservices. The client computing devices may be configured to operate aclient application such as a web browser, a proprietary clientapplication (e.g., Oracle Forms), or some other application, which maybe used by a user of the client computing device to interact with cloudinfrastructure system 1002 to use services provided by cloudinfrastructure system 1002.

It should be appreciated that cloud infrastructure system 1002 depictedin the figure may have other components than those depicted. Further,the embodiment shown in the figure is only one example of a cloudinfrastructure system that may incorporate an embodiment of theinvention. In some other embodiments, cloud infrastructure system 1002may have more or fewer components than shown in the figure, may combinetwo or more components, or may have a different configuration orarrangement of components.

Client computing devices 1004, 1006, and 1008 may be devices similar tothose described above for 902, 904, 906, and 908.

Although exemplary system environment 1000 is shown with three clientcomputing devices, any number of client computing devices may besupported. Other devices such as devices with sensors, etc. may interactwith cloud infrastructure system 1002.

Network(s) 1010 may facilitate communications and exchange of databetween clients 1004, 1006, and 1008 and cloud infrastructure system1002. Each network may be any type of network familiar to those skilledin the art that can support data communications using any of a varietyof commercially-available protocols, including those described above fornetwork(s) 910.

Cloud infrastructure system 1002 may comprise one or more computersand/or servers that may include those described above for server 912.

In certain embodiments, services provided by the cloud infrastructuresystem may include a host of services that are made available to usersof the cloud infrastructure system on demand, such as online datastorage and backup solutions, Web-based e-mail services, hosted officesuites and document collaboration services, database processing, managedtechnical support services, and the like. Services provided by the cloudinfrastructure system can dynamically scale to meet the needs of itsusers. A specific instantiation of a service provided by cloudinfrastructure system is referred to herein as a “service instance.” Ingeneral, any service made available to a user via a communicationnetwork, such as the Internet, from a cloud service provider's system isreferred to as a “cloud service.” Typically, in a public cloudenvironment, servers and systems that make up the cloud serviceprovider's system are different from the customer's own on-premisesservers and systems. For example, a cloud service provider's system mayhost an application, and a user may, via a communication network such asthe Internet, on demand, order and use the application.

In some examples, a service in a computer network cloud infrastructuremay include protected computer network access to storage, a hosteddatabase, a hosted web server, a software application, or other serviceprovided by a cloud vendor to a user, or as otherwise known in the art.For example, a service can include password-protected access to remotestorage on the cloud through the Internet. As another example, a servicecan include a web service-based hosted relational database and ascript-language middleware engine for private use by a networkeddeveloper. As another example, a service can include access to an emailsoftware application hosted on a cloud vendor's web site.

In certain embodiments, cloud infrastructure system 1002 may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner. Anexample of such a cloud infrastructure system is the Oracle Public Cloudprovided by the present assignee.

In various embodiments, cloud infrastructure system 1002 may be adaptedto automatically provision, manage and track a customer's subscriptionto services offered by cloud infrastructure system 1002. Cloudinfrastructure system 1002 may provide the cloud services via differentdeployment models. For example, services may be provided under a publiccloud model in which cloud infrastructure system 1002 is owned by anorganization selling cloud services (e.g., owned by Oracle) and theservices are made available to the general public or different industryenterprises. As another example, services may be provided under aprivate cloud model in which cloud infrastructure system 1002 isoperated solely for a single organization and may provide services forone or more entities within the organization. The cloud services mayalso be provided under a community cloud model in which cloudinfrastructure system 1002 and the services provided by cloudinfrastructure system 1002 are shared by several organizations in arelated community. The cloud services may also be provided under ahybrid cloud model, which is a combination of two or more differentmodels.

In some embodiments, the services provided by cloud infrastructuresystem 1002 may include one or more services provided under Software asa Service (SaaS) category, Platform as a Service (PaaS) category,Infrastructure as a Service (IaaS) category, or other categories ofservices including hybrid services. A customer, via a subscriptionorder, may order one or more services provided by cloud infrastructuresystem 1002. Cloud infrastructure system 1002 then performs processingto provide the services in the customer's subscription order.

In some embodiments, the services provided by cloud infrastructuresystem 1002 may include, without limitation, application services,platform services and infrastructure services. In some examples,application services may be provided by the cloud infrastructure systemvia a SaaS platform. The SaaS platform may be configured to providecloud services that fall under the SaaS category. For example, the SaaSplatform may provide capabilities to build and deliver a suite ofon-demand applications on an integrated development and deploymentplatform. The SaaS platform may manage and control the underlyingsoftware and infrastructure for providing the SaaS services. Byutilizing the services provided by the SaaS platform, customers canutilize applications executing on the cloud infrastructure system.Customers can acquire the application services without the need forcustomers to purchase separate licenses and support. Various differentSaaS services may be provided. Examples include, without limitation,services that provide solutions for sales performance management,enterprise integration, and business flexibility for largeorganizations.

In some embodiments, platform services may be provided by the cloudinfrastructure system via a PaaS platform. The PaaS platform may beconfigured to provide cloud services that fall under the PaaS category.Examples of platform services may include without limitation servicesthat enable organizations (such as Oracle) to consolidate existingapplications on a shared, common architecture, as well as the ability tobuild new applications that leverage the shared services provided by theplatform. The PaaS platform may manage and control the underlyingsoftware and infrastructure for providing the PaaS services. Customerscan acquire the PaaS services provided by the cloud infrastructuresystem without the need for customers to purchase separate licenses andsupport. Examples of platform services include, without limitation,Oracle Java Cloud Service (JCS), Oracle Database Cloud Service (DBCS),and others.

By utilizing the services provided by the PaaS platform, customers canemploy programming languages and tools supported by the cloudinfrastructure system and also control the deployed services. In someembodiments, platform services provided by the cloud infrastructuresystem may include database cloud services, middleware cloud services(e.g., Oracle Fusion Middleware services), and Java cloud services. Inone embodiment, database cloud services may support shared servicedeployment models that enable organizations to pool database resourcesand offer customers a Database as a Service in the form of a databasecloud. Middleware cloud services may provide a platform for customers todevelop and deploy various business applications, and Java cloudservices may provide a platform for customers to deploy Javaapplications, in the cloud infrastructure system.

Various different infrastructure services may be provided by an IaaSplatform in the cloud infrastructure system. The infrastructure servicesfacilitate the management and control of the underlying computingresources, such as storage, networks, and other fundamental computingresources for customers utilizing services provided by the SaaS platformand the PaaS platform.

In certain embodiments, cloud infrastructure system 1002 may alsoinclude infrastructure resources 1030 for providing the resources usedto provide various services to customers of the cloud infrastructuresystem. In one embodiment, infrastructure resources 1030 may includepre-integrated and optimized combinations of hardware, such as servers,storage, and networking resources to execute the services provided bythe PaaS platform and the SaaS platform.

In some embodiments, resources in cloud infrastructure system 1002 maybe shared by multiple users and dynamically re-allocated per demand.Additionally, resources may be allocated to users in different timezones. For example, cloud infrastructure system 1030 may enable a firstset of users in a first time zone to utilize resources of the cloudinfrastructure system for a specified number of hours and then enablethe re-allocation of the same resources to another set of users locatedin a different time zone, thereby maximizing the utilization ofresources.

In certain embodiments, a number of internal shared services 1032 may beprovided that are shared by different components or modules of cloudinfrastructure system 1002 and by the services provided by cloudinfrastructure system 1002. These internal shared services may include,without limitation, a security and identity service, an integrationservice, an enterprise repository service, an enterprise managerservice, a virus scanning and white list service, a high availability,backup and recovery service, service for enabling cloud support, anemail service, a notification service, a file transfer service, and thelike.

In certain embodiments, cloud infrastructure system 1002 may providecomprehensive management of cloud services (e.g., SaaS, PaaS, and IaaSservices) in the cloud infrastructure system. In one embodiment, cloudmanagement functionality may include capabilities for provisioning,managing and tracking a customer's subscription received by cloudinfrastructure system 1002, and the like.

In one embodiment, as depicted in the figure, cloud managementfunctionality may be provided by one or more modules, such as an ordermanagement module 1020, an order orchestration module 1022, an orderprovisioning module 1024, an order management and monitoring module1026, and an identity management module 1028. These modules may includeor be provided using one or more computers and/or servers, which may begeneral purpose computers, specialized server computers, server farms,server clusters, or any other appropriate arrangement and/orcombination.

In exemplary operation 1034, a customer using a client device, such asclient device 1004, 1006 or 1008, may interact with cloud infrastructuresystem 1002 by requesting one or more services provided by cloudinfrastructure system 1002 and placing an order for a subscription forone or more services offered by cloud infrastructure system 1002. Incertain embodiments, the customer may access a cloud User Interface(UI), cloud UI 1012, cloud UI 1014 and/or cloud UI 1016 and place asubscription order via these UIs. The order information received bycloud infrastructure system 1002 in response to the customer placing anorder may include information identifying the customer and one or moreservices offered by the cloud infrastructure system 1002 that thecustomer intends to subscribe to.

After an order has been placed by the customer, the order information isreceived via the cloud UIs, 1012, 1014 and/or 1016.

At operation 1036, the order is stored in order database 1018. Orderdatabase 1018 can be one of several databases operated by cloudinfrastructure system 1018 and operated in conjunction with other systemelements.

At operation 1038, the order information is forwarded to an ordermanagement module 1020. In some instances, order management module 1020may be configured to perform billing and accounting functions related tothe order, such as verifying the order, and upon verification, bookingthe order.

At operation 1040, information regarding the order is communicated to anorder orchestration module 1022. Order orchestration module 1022 mayutilize the order information to orchestrate the provisioning ofservices and resources for the order placed by the customer. In someinstances, order orchestration module 1022 may orchestrate theprovisioning of resources to support the subscribed services using theservices of order provisioning module 1024.

In certain embodiments, order orchestration module 1022 enables themanagement of business processes associated with each order and appliesbusiness logic to determine whether an order should proceed toprovisioning. At operation 1042, upon receiving an order for a newsubscription, order orchestration module 1022 sends a request to orderprovisioning module 1024 to allocate resources and configure thoseresources needed to fulfill the subscription order. Order provisioningmodule 1024 enables the allocation of resources for the services orderedby the customer. Order provisioning module 1024 provides a level ofabstraction between the cloud services provided by cloud infrastructuresystem 1000 and the physical implementation layer that is used toprovision the resources for providing the requested services. Orderorchestration module 1022 may thus be isolated from implementationdetails, such as whether or not services and resources are actuallyprovisioned on the fly or pre-provisioned and only allocated/assignedupon request.

At operation 1044, once the services and resources are provisioned, anotification of the provided service may be sent to customers on clientdevices 1004, 1006 and/or 1008 by order provisioning module 1024 ofcloud infrastructure system 1002.

At operation 1046, the customer's subscription order may be managed andtracked by an order management and monitoring module 1026. In someinstances, order management and monitoring module 1026 may be configuredto collect usage statistics for the services in the subscription order,such as the amount of storage used, the amount data transferred, thenumber of users, and the amount of system up time and system down time.

In certain embodiments, cloud infrastructure system 1000 may include anidentity management module 1028. Identity management module 1028 may beconfigured to provide identity services, such as access management andauthorization services in cloud infrastructure system 1000. In someembodiments, identity management module 1028 may control informationabout customers who wish to utilize the services provided by cloudinfrastructure system 1002. Such information can include informationthat authenticates the identities of such customers and information thatdescribes which actions those customers are authorized to performrelative to various system resources (e.g., files, directories,applications, communication ports, memory segments, etc.) Identitymanagement module 1028 may also include the management of descriptiveinformation about each customer and about how and by whom thatdescriptive information can be accessed and modified.

FIG. 25 illustrates an example computer system 2500 in which variousembodiments of the present invention may be implemented. The system 2500may be used to implement any of the computer systems described above. Asshown in the figure, computer system 2500 includes a processing unit2504 that communicates with a number of peripheral subsystems via a bussubsystem 2502. These peripheral subsystems may include a processingacceleration unit 2506, an I/O subsystem 2508, a storage subsystem 2518and a communications subsystem 2524. Storage subsystem 2518 includestangible computer-readable storage media 2522 and a system memory 2510.

Bus subsystem 2502 provides a mechanism for letting the variouscomponents and subsystems of computer system 2500 communicate with eachother as intended. Although bus subsystem 2502 is shown schematically asa single bus, alternative embodiments of the bus subsystem may utilizemultiple buses. Bus subsystem 2502 may be any of several types of busstructures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. Forexample, such architectures may include an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which can beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 2504, which can be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of computer system 2500. One or more processorsmay be included in processing unit 2504. These processors may includesingle core or multicore processors. In certain embodiments, processingunit 2504 may be implemented as one or more independent processing units2532 and/or 2534 with single or multicore processors included in eachprocessing unit. In other embodiments, processing unit 2504 may also beimplemented as a quad-core processing unit formed by integrating twodual-core processors into a single chip.

In various embodiments, processing unit 2504 can execute a variety ofprograms in response to program code and can maintain multipleconcurrently executing programs or processes. At any given time, some orall of the program code to be executed can be resident in processor(s)2504 and/or in storage subsystem 2518. Through suitable programming,processor(s) 2504 can provide various functionalities described above.Computer system 2500 may additionally include a processing accelerationunit 2506, which can include a digital signal processor (DSP), aspecial-purpose processor, and/or the like.

I/O subsystem 2508 may include user interface input devices and userinterface output devices. User interface input devices may include akeyboard, pointing devices such as a mouse or trackball, a touchpad ortouch screen incorporated into a display, a scroll wheel, a click wheel,a dial, a button, a switch, a keypad, audio input devices with voicecommand recognition systems, microphones, and other types of inputdevices. User interface input devices may include, for example, motionsensing and/or gesture recognition devices such as the Microsoft Kinect®motion sensor that enables users to control and interact with an inputdevice, such as the Microsoft Xbox® 360 game controller, through anatural user interface using gestures and spoken commands. Userinterface input devices may also include eye gesture recognition devicessuch as the Google Glass® blink detector that detects eye activity(e.g., ‘blinking’ while taking pictures and/or making a menu selection)from users and transforms the eye gestures as input into an input device(e.g., Google Glass®). Additionally, user interface input devices mayinclude voice recognition sensing devices that enable users to interactwith voice recognition systems (e.g., Siri® navigator), through voicecommands.

User interface input devices may also include, without limitation, threedimensional (3D) mice, joysticks or pointing sticks, gamepads andgraphic tablets, and audio/visual devices such as speakers, digitalcameras, digital camcorders, portable media players, webcams, imagescanners, fingerprint scanners, barcode reader 3D scanners, 3D printers,laser rangefinders, and eye gaze tracking devices. Additionally, userinterface input devices may include, for example, medical imaging inputdevices such as computed tomography, magnetic resonance imaging,position emission tomography, medical ultrasonography devices. Userinterface input devices may also include, for example, audio inputdevices such as MIDI keyboards, digital musical instruments and thelike.

User interface output devices may include a display subsystem, indicatorlights, or non-visual displays such as audio output devices, etc. Thedisplay subsystem may be a cathode ray tube (CRT), a flat-panel device,such as that using a liquid crystal display (LCD) or plasma display, aprojection device, a touch screen, and the like. In general, use of theterm “output device” is intended to include all possible types ofdevices and mechanisms for outputting information from computer system2500 to a user or other computer. For example, user interface outputdevices may include, without limitation, a variety of display devicesthat visually convey text, graphics and audio/video information such asmonitors, printers, speakers, headphones, automotive navigation systems,plotters, voice output devices, and modems.

Computer system 2500 may comprise a storage subsystem 2518 thatcomprises software elements, shown as being currently located within asystem memory 2510. System memory 2510 may store program instructionsthat are loadable and executable on processing unit 2504, as well asdata generated during the execution of these programs.

Depending on the configuration and type of computer system 2500, systemmemory 2510 may be volatile (such as random access memory (RAM)) and/ornon-volatile (such as read-only memory (ROM), flash memory, etc.) TheRAM typically contains data and/or program modules that are immediatelyaccessible to and/or presently being operated and executed by processingunit 2504. In some implementations, system memory 2510 may includemultiple different types of memory, such as static random access memory(SRAM) or dynamic random access memory (DRAM). In some implementations,a basic input/output system (BIOS), containing the basic routines thathelp to transfer information between elements within computer system2500, such as during start-up, may typically be stored in the ROM. Byway of example, and not limitation, system memory 2510 also illustratesapplication programs 2512, which may include client applications, Webbrowsers, mid-tier applications, relational database management systems(RDBMS), etc., program data 2514, and an operating system 2516. By wayof example, operating system 2516 may include various versions ofMicrosoft Windows®, Apple Macintosh®, and/or Linux operating systems, avariety of commercially-available UNIX® or UNIX-like operating systems(including without limitation the variety of GNU/Linux operatingsystems, the Google Chrome® OS, and the like) and/or mobile operatingsystems such as iOS, Windows® Phone, Android® OS, BlackBerry® 25 OS, andPalm® OS operating systems.

Storage subsystem 2518 may also provide a tangible computer-readablestorage medium for storing the basic programming and data constructsthat provide the functionality of some embodiments. Software (programs,code modules, instructions) that when executed by a processor providethe functionality described above may be stored in storage subsystem2518. These software modules or instructions may be executed byprocessing unit 2504. Storage subsystem 2518 may also provide arepository for storing data used in accordance with the presentinvention.

Storage subsystem 2500 may also include a computer-readable storagemedia reader 2520 that can further be connected to computer-readablestorage media 2522. Together and, optionally, in combination with systemmemory 2510, computer-readable storage media 2522 may comprehensivelyrepresent remote, local, fixed, and/or removable storage devices plusstorage media for temporarily and/or more permanently containing,storing, transmitting, and retrieving computer-readable information.

Computer-readable storage media 2522 containing code, or portions ofcode, can also include any appropriate media known or used in the art,including storage media and communication media, such as but not limitedto, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information. This can include tangible computer-readable storagemedia such as RAM, ROM, electronically erasable programmable ROM(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible computer readable media. This can also includenontangible computer-readable media, such as data signals, datatransmissions, or any other medium which can be used to transmit thedesired information and which can be accessed by computing system 2500.

By way of example, computer-readable storage media 2522 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray® disk, or other optical media.Computer-readable storage media 2522 may include, but is not limited to,Zip® drives, flash memory cards, universal serial bus (USB) flashdrives, secure digital (SD) cards, DVD disks, digital video tape, andthe like. Computer-readable storage media 2522 may also include,solid-state drives (SSD) based on non-volatile memory such asflash-memory based SSDs, enterprise flash drives, solid state ROM, andthe like, SSDs based on volatile memory such as solid state RAM, dynamicRAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, andhybrid SSDs that use a combination of DRAM and flash memory based SSDs.The disk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for computer system 2500.

Communications subsystem 2524 provides an interface to other computersystems and networks. Communications subsystem 2524 serves as aninterface for receiving data from and transmitting data to other systemsfrom computer system 2500. For example, communications subsystem 2524may enable computer system 2500 to connect to one or more devices viathe Internet. In some embodiments communications subsystem 2524 caninclude radio frequency (RF) transceiver components for accessingwireless voice and/or data networks (e.g., using cellular telephonetechnology, advanced data network technology, such as 3G, 4G or EDGE(enhanced data rates for global evolution), WiFi (IEEE 802.11 familystandards, or other mobile communication technologies, or anycombination thereof), global positioning system (GPS) receivercomponents, and/or other components. In some embodiments communicationssubsystem 2524 can provide wired network connectivity (e.g., Ethernet)in addition to or instead of a wireless interface.

In some embodiments, communications subsystem 2524 may also receiveinput communication in the form of structured and/or unstructured datafeeds 2526, event streams 2528, event updates 2530, and the like onbehalf of one or more users who may use computer system 2500.

By way of example, communications subsystem 2524 may be configured toreceive data feeds 2526 in real-time from users of social networksand/or other communication services such as Twitter® feeds, Facebook®updates, web feeds such as Rich Site Summary (RSS) feeds, and/orreal-time updates from one or more third party information sources.

Additionally, communications subsystem 2524 may also be configured toreceive data in the form of continuous data streams, which may includeevent streams 2528 of real-time events and/or event updates 2530, whichmay be continuous or unbounded in nature with no explicit end. Examplesof applications that generate continuous data may include, for example,sensor data applications, financial tickers, network performancemeasuring tools (e.g. network monitoring and traffic managementapplications), clickstream analysis tools, automobile trafficmonitoring, and the like. Communications subsystem 2524 may also beconfigured to output the structured and/or unstructured data feeds 2526,event streams 2528, event updates 2530, and the like to one or moredatabases that may be in communication with one or more streaming datasource computers coupled to computer system 2500.

Computer system 2500 can be one of various types, including a handheldportable device (e.g., an iPhone® cellular phone, an iPad® computingtablet, a PDA), a wearable device (e.g., a Google Glass® head mounteddisplay), a PC, a workstation, a mainframe, a kiosk, a server rack, orany other data processing system.

Due to the ever-changing nature of computers and networks, thedescription of computer system 2500 depicted in the figure is intendedonly as a specific example. Many other configurations having more orfewer components than the system depicted in the figure are possible.For example, customized hardware might also be used and/or particularelements might be implemented in hardware, firmware, software (includingapplets), or a combination. Further, connection to other computingdevices, such as network input/output devices, may be employed. Based onthe disclosure and teachings provided herein, a person of ordinary skillin the art will appreciate other ways and/or methods to implement thevarious embodiments.

In the foregoing specification, aspects of the invention are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the invention is not limited thereto. Variousfeatures and aspects of the above-described invention may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

What is claimed is:
 1. A method of automatically rendering a flowdiagram, the method comprising: receiving, at a computing device, userinput that specifies a key status; generating a network of relationshipsbetween the key status and one or more other statuses; determining flowsfor connections between the statuses in the network based on quantitiesof objects that flowed between the statuses in the network during aspecified time period; ranking the connections based on flows determinedfor the connections; selecting a subset of the ranked connections;determining a critical path based on the subset of the rankedconnections; and rendering the flow diagram including the critical path.2. The method of claim 1, further comprising: receiving a user commandto automatically draw the flow diagram; and generating the network ofrelationships in response to receiving the user command.
 3. The methodof claim 1, wherein selecting the subset of ranked connections comprisesselecting at least a specified minimum quantity of the rankedconnections.
 4. The method of claim 1, further comprising: receivinguser input that requests increase in zoom; and in response to receivingthe user input that requests increase in zoom, re-rendering the flowdiagram at a different zoom level than a zoom level at which the flowdiagram had been rendered.
 5. The method of claim 1, wherein generatingthe network of relationships comprises: receiving user input specifyingthe time period; gathering, from snapshots, data pertaining to points intime during the specified time period; for each particular status in aset of selected statuses that initially includes only the key status,determining, based on the snapshots, a first set of other statusesobjects possessed prior to assuming the particular status, and a secondset of other statuses objects assumed after possessing the particularstatus; determining whether a current zoom level is equal to a targetzoom level; in response to determining that the current zoom level isnot equal to the target zoom level, incrementing the current zoom level,including at least some of the first and second sets of statuses in theset of selected statuses, and repeating said determining of said firstand second sets.
 6. A computer-implemented method comprising:automatically selecting, based on specified criteria, and from a set ofstatuses, a subset of statuses designated to be significant statuses;automatically positioning flow elements corresponding to statuses fromthe subset of statuses in a portion of a diagram that is initiallypresented on a display; automatically positioning one or more flowelements contained in the set of statuses, but not in the subset ofstatuses, in a portion of the diagram that is not initially presented onthe display; and presenting, on the display, the portion of the diagramthat is initially presented on the display.
 7. The computer-implementedmethod of claim 7, further comprising: receiving user input thatspecifies a network depth; and automatically generating, in the diagram,chains of connected flow elements limited to quantities of flow elementsthat are based on the user input.
 8. The computer-implemented method ofclaim 7, further comprising: receiving user input that specifies athreshold that represents a detail level; automatically selecting, forrepresentation in the diagram, from the set of statuses, only statusesthat are endpoints of connections through which a quantity of objectsthat is greater than or equal to the specified threshold flowed during aspecified time period.
 9. The computer-implemented method of claim 7,wherein automatically selecting the subset of statuses designated to besignificant statuses comprises: for each particular status in the set ofstatuses, determining a quantity of objects that changed from thatparticular status to another status during a specified time period; andranking statuses in the set of statuses based on said quantities ofobjects that changed from those statuses to other statuses during thespecified time period; and selecting one or more statuses from the setof statuses for inclusion in the subset of statuses based on saidrankings of statuses in the set of statuses.
 10. Thecomputer-implemented method of claim 7, wherein automatically selectingthe subset of statuses designated to be significant statuses comprises:for each particular status in the set of statuses, determining aquantity of objects that changed from another status to that particularstatus during a specified time period; and ranking incoming statuses inthe set of statuses based on said quantities of objects that changedfrom other statuses to those incoming statuses during the specified timeperiod; and selecting one or more statuses from the set of statuses forinclusion in the subset of statuses based on said rankings of incomingstatuses in the set of statuses.
 11. The computer-implemented method ofclaim 7, further comprising: excluding, from the diagram, connectionsthrough which less than a specified quantity of objects flowed betweenflow elements during a specified time period.
 12. Thecomputer-implemented method of claim 7, further comprising: prior toadding any other connections to the flow diagram, adding, to the flowdiagram, direct connections between pairs of flow elements correspondingto pairs statuses that are both in the subset and that are related dueto objects changing from one status in the pair directly to anotherstatus in the pair; and after adding the direct connections to the flowdiagram, adding, to the flow diagram, one or more additional connectionsneeded to ensure that at least one path exists between each element inthe flow diagram to each other flow element in the diagram.
 13. Anon-transitory computer-readable storage medium storing instructionswhich, when executed by one or more processors, cause the processors toperform operations comprising: automatically selecting, based onspecified criteria, and from a set of statuses, a subset of statusesdesignated to be significant statuses; automatically positioning flowelements corresponding to statuses from the subset of statuses in aportion of a diagram that is initially presented on a display;automatically positioning one or more flow elements contained in the setof statuses, but not in the subset of statuses, in a portion of thediagram that is not initially presented on the display; and presenting,on the display, the portion of the diagram that is initially presentedon the display.
 14. The non-transitory computer-readable storage mediumof claim 14, said operations further comprising: receiving user inputthat specifies a network depth; and automatically generating, in thediagram, chains of connected flow elements limited to quantities of flowelements that are based on the user input.
 15. The non-transitorycomputer-readable storage medium of claim 14, said operations furthercomprising: receiving user input that specifies a threshold thatrepresents a detail level; automatically selecting, for representationin the diagram, from the set of statuses, only statuses that areendpoints of connections through which a quantity of objects that isgreater than or equal to the specified threshold flowed during aspecified time period.
 16. The non-transitory computer-readable storagemedium of claim 14, wherein automatically selecting the subset ofstatuses designated to be significant statuses comprises: for eachparticular status in the set of statuses, determining a quantity ofobjects that changed from that particular status to another statusduring a specified time period; and ranking statuses in the set ofstatuses based on said quantities of objects that changed from thosestatuses to other statuses during the specified time period; andselecting one or more statuses from the set of statuses for inclusion inthe subset of statuses based on said rankings of statuses in the set ofstatuses.
 17. The non-transitory computer-readable storage medium ofclaim 14, wherein automatically selecting the subset of statusesdesignated to be significant statuses comprises: for each particularstatus in the set of statuses, determining a quantity of objects thatchanged from another status to that particular status during a specifiedtime period; and ranking incoming statuses in the set of statuses basedon said quantities of objects that changed from other statuses to thoseincoming statuses during the specified time period; and selecting one ormore statuses from the set of statuses for inclusion in the subset ofstatuses based on said rankings of incoming statuses in the set ofstatuses.
 18. The non-transitory computer-readable storage medium ofclaim 14, said operations further comprising: excluding, from thediagram, connections through which less than a specified quantity ofobjects flowed between flow elements during a specified time period. 19.The non-transitory computer-readable storage medium of claim 14, saidoperations further comprising: prior to adding any other connections tothe flow diagram, adding, to the flow diagram, direct connectionsbetween pairs of flow elements corresponding to pairs statuses that areboth in the subset and that are related due to objects changing from onestatus in the pair directly to another status in the pair; and afteradding the direct connections to the flow diagram, adding, to the flowdiagram, one or more additional connections needed to ensure that atleast one path exists between each element in the flow diagram to eachother flow element in the diagram.